Systems and methods for executing ecommerce guest checkout transactions

ABSTRACT

Systems and methods are disclosed for executing an electronic transaction using a digital wallet. One method includes receiving a guest checkout request and electronic transaction data from an electronic transaction browser. Whether a user is enrolled in the digital wallet system may be determined by the digital wallet system. The digital wallet system may authorize an electronic transaction based on the electronic transaction data upon determining the user is not enrolled in the digital wallet system. The digital wallet system may initiate a digital wallet enrollment upon authorizing the electronic transaction. The digital wallet system may store the user data in the digital wallet system and transmit a verification request to the electronic transaction browser. The digital wallet system may receive a verification response from the electronic transaction browser and may generate a digital wallet enrollment status message based on the verification response.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of and claims the benefit of priorityfrom U.S. Nonprovisional application Ser. No. 17/106,654, filed on Nov.30, 2020, which claims the benefit of priority to U.S. ProvisionalApplication No. 62/705,037, filed on Jun. 8, 2020, which is herebyincorporated herein by reference in its entirety.

PRIORITY

This application claims the benefit of priority from ProvisionalApplication No. 62/705,037 filed Jun. 8, 2020, which is herebyincorporated herein by reference in its entirety

TECHNICAL FIELD

The present disclosure relates generally to the field of electronictransactions and, more particularly, to systems and methods forexecuting electronic transactions, including tokenized transactions.

BACKGROUND

Digital wallets store consumer credentials and payment information toenable consumers to make electronic purchases and perform other onlinefinancial transactions. Typically, customers enroll into digital walletservices on merchant websites. The customers, however, are required tomanually enter personal and financial information into a lengthy list ofinput fields provided on the merchant website in order to enroll intodigital wallet services. The present disclosure is directed toaddressing these and other drawbacks to existing digital walletservices.

The background description provided herein is for the purpose ofgenerally presenting context of the disclosure. Unless otherwiseindicated herein, the materials described in this section are not priorart to the claims in this application and are not admitted to be priorart, or suggestions of the prior art, by inclusion in this section.

SUMMARY OF THE DISCLOSURE

One embodiment provides a method for executing an electronic transactionusing a digital wallet, comprising: receiving, from an electronictransaction browser, a guest checkout request and electronic transactiondata, the electronic transaction data including user data; determining,by a digital wallet system, whether a user is enrolled in the digitalwallet system; upon determining the user is not enrolled in the digitalwallet system, authorizing, by the digital wallet system, an electronictransaction based on the electronic transaction data; upon authorizingthe electronic transaction, initiating, by the digital wallet system, adigital wallet enrollment; storing, by the digital wallet system, theuser data in the digital wallet system; transmitting, by the digitalwallet system, a verification request to the electronic transactionbrowser; receiving, by the digital wallet system, a verificationresponse from the electronic transaction browser; and generating, by thedigital wallet system, a digital wallet enrollment status message basedon the verification response.

One embodiment provides a system comprising: one or more computerreadable media storing instructions for executing an electronictransaction using a digital wallet; and one or more processorsconfigured to execute the instructions to perform operations comprising:receiving, from an electronic transaction browser, a guest checkoutrequest and electronic transaction data, the electronic transaction dataincluding user data; determining, by a digital wallet system, whether auser is enrolled in the digital wallet system; upon determining the useris not enrolled in the digital wallet system, authorizing, by thedigital wallet system, an electronic transaction based on the electronictransaction data; upon authorizing the electronic transaction,initiating, by the digital wallet system, a digital wallet enrollment;storing, by the digital wallet system, the user data in the digitalwallet system; transmitting, by the digital wallet system, averification request to the electronic transaction browser; receiving,by the digital wallet system, a verification response from theelectronic transaction browser; and generating, by the digital walletsystem, a digital wallet enrollment status message based on theverification response.

One embodiment provides a non-transitory computer-readable mediumstoring instructions for executing an electronic transaction using adigital wallet, the instructions, when executed by one or moreprocessors, causing the one or more processors to perform operationscomprising: receiving, from an electronic transaction browser, a guestcheckout request and electronic transaction data, the electronictransaction data including user data; determining, by a digital walletsystem, whether a user is enrolled in the digital wallet system; upondetermining the user is not enrolled in the digital wallet system,authorizing, by the digital wallet system, an electronic transactionbased on the electronic transaction data; upon authorizing theelectronic transaction, initiating, by the digital wallet system, adigital wallet enrollment; storing, by the digital wallet system, theuser data in the digital wallet system; transmitting, by the digitalwallet system, a verification request to the electronic transactionbrowser; receiving, by the digital wallet system, a verificationresponse from the electronic transaction browser; and generating, by thedigital wallet system, a digital wallet enrollment status message basedon the verification response.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate several embodiments and togetherwith the description, serve to explain the principles of the disclosure.

FIG. 1 depicts a block diagram of an exemplary electronic transactionsystem, according to one aspect of the present disclosure.

FIG. 2 depicts a block diagram of an exemplary digital wallet system,according to one aspect of the present disclosure.

FIG. 3 depicts a flowchart of an exemplary method of executing a digitalwallet enrollment and/or transaction, according to one aspect of thepresent disclosure.

FIG. 4 depicts a flowchart of another exemplary method of executing adigital wallet enrollment and/or transaction, according to one aspect ofthe present disclosure.

FIG. 5 depicts a flowchart of yet another exemplary method of executinga digital wallet enrollment and transaction, according to one aspect ofthe present disclosure.

FIG. 6 depicts a flowchart of yet another exemplary method of executinga digital wallet enrollment and/or transaction, according to one aspectof the present disclosure.

FIGS. 7A, 7B, 8A, and 8B show exemplary interfaces for executing adigital wallet enrollment and/or transaction, according to one aspect ofthe present disclosure.

FIG. 9A depicts a flowchart of an exemplary method of executing adigital wallet enrollment and transaction, according to one aspect ofthe present disclosure.

FIG. 9B depicts a flowchart of another exemplary method executing adigital wallet enrollment and/or transaction, according to one aspect ofthe present disclosure.

FIG. 9C depicts a flowchart of yet another exemplary method of executinga digital wallet enrollment and/or transaction, according to one aspectof the present disclosure.

FIG. 10 illustrates a computer system for executing the techniquesdescribed herein.

DETAILED DESCRIPTION OF EMBODIMENTS

The following embodiments describe systems and methods for securely andefficiently facilitating electronic transactions using a digital wallet.More particularly, the embodiments contemplated in the presentdisclosure may enable merchants and customers to utilize a digitalwallet service provided by a processing system, which may be configuredto perform digital wallet transactions, tokenization of sensitive userand payment data, and/or electronic transaction authorizations.

Conventionally, digital wallet systems and services utilize techniquesto solicit user enrollment during various online transactions, such asduring online shopping. However, such techniques require users (orcustomers) to manually input information (e.g., name, email address,physical address, credit card information, bank account information,etc.) into a lengthy list of data fields on a website in order toestablish digital wallet accounts. Such a requirement causes frictionthat turns many users away prematurely, causing abandonment of thedigital wallet enrollment process or online shopping altogether. Theusers who opt-out of enrolling into the digital wallet services andchoose to complete their online purchase transactions through guestcheckouts face similar issues. That is, the users who choose guestcheckouts must also manually enter lengthy personal and financialinformation in order to complete their purchases, causing inconvenienceand potential abandonment of purchase transactions. Moreover, many usersare hesitant about enrolling in digital wallet services due to securityconcerns regarding their personal and financial credentials.

To address the above-noted problems, the present disclosure describesdigital wallet systems and methods that facilitate a digital walletenrollment and/or transaction process before, during, or after apurchase transaction. For example, the digital wallet system of thepresent disclosure may determine, before completing a purchasetransaction, whether a user is enrolled in the digital wallet system.The user enrollment may be determined based on the information (e.g.,email address or phone number) that the user has provided during aprevious purchase transaction. If the user is not enrolled in thedigital wallet service, the digital wallet system may initiate a digitalwallet enrollment process by performing a one-time passwordauthentication (OTPA) or a two-factor authentication (2FA) with theuser. Additionally or alternatively, the digital wallet system of thepresent disclosure may determine whether a user is enrolled in thedigital wallet system during guest checkout or express checkout (e.g., aservice provided by the digital wallet system). If the user is enrolledin the digital wallet system, the digital wallet system may providevarious digital wallet services (e.g., express checkout, auto-populatingsaved user data, tokenization, payment options, etc.). If the user isnot enrolled in the digital wallet system, however, the digital walletsystem may initiate an enrollment process after completing the purchasetransaction. As such, users may utilize the digital wallet servicesoffered by the digital wallet system without friction, regardless ofwhether the user chooses to complete the purchase transaction via aguest checkout or an express checkout. Moreover, the digital walletsystem of the present disclosure may generate or exchange digital wallettokens based on the payment information provided by the users andmerchants who are enrolled in the digital wallet system, eliminatingsecurity concerns regarding any sensitive user data provided during thepurchase transactions.

It should be appreciated that particular consideration is made herein topurchase transactions relating to merchants. Despite this reference topurchase transactions relating to merchants, certain disclosed systemsand methods may apply equally well to the various e-commercetransactions. Effectively, any circumstance where sensitive data, suchas a PAN, a PIN, a social security number, etc., or a tokencorresponding thereto, is being transmitted over a network, systems andmethods disclosed herein may be employed. Further, while the partyseeking to initiate a secure transaction and/or provide a third-partyservice may be referred to herein as a “merchant,” a party seeking toinitiate a secure transaction need not be a merchant, but may be aservice provider, or any party seeking to execute a transaction.

The subject matter of the present disclosure will now be described morefully hereinafter with reference to the accompanying drawings, whichform a part hereof, and which show, by way of illustration, specificexemplary embodiments. An embodiment or implementation described hereinas “exemplary” is not to be construed as preferred or advantageous, forexample, over other embodiments or implementations; rather, it isintended to reflect or indicate that the embodiment(s) is/are “example”embodiment(s). Subject matter may be embodied in a variety of differentforms and, therefore, covered or claimed subject matter is intended tobe construed as not being limited to any exemplary embodiments set forthherein; exemplary embodiments are provided merely to be illustrative.Likewise, a reasonably broad scope for claimed or covered subject matteris intended. Among other things, for example, subject matter may beembodied as methods, devices, components, or systems. Accordingly,embodiments may, for example, take the form of hardware, software,firmware or any combination thereof. The following detailed descriptionis, therefore, not intended to be taken in a limiting sense.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, the phrase “in one embodiment” or “in some embodiments” asused herein does not necessarily refer to the same embodiment and thephrase “in another embodiment” as used herein does not necessarily referto a different embodiment. It is intended, for example, that claimedsubject matter include combinations of exemplary embodiments in whole orin part.

The terminology used below may be interpreted in its broadest reasonablemanner, even though it is being used in conjunction with a detaileddescription of certain specific examples of the present disclosure.Indeed, certain terms may even be emphasized below; however, anyterminology intended to be interpreted in any restricted manner will beovertly and specifically defined as such in this Detailed Descriptionsection.

Referring now to the appended drawings, FIG. 1 depicts an exemplaryelectronic transaction system 100 including a browser 110, a merchantsystem 120, and a processing system 130, which is in communication witha transaction network 170. The browser 110 may display a website hostedby the merchant system 120. The browser 110 may be a client-side browseron a user computing device, but may also be a client-side app or websitefor performing e-commerce electronic transactions, or any other type ofsoftware or application on a client-side data processor. A user 105 mayaccess the website hosted by the merchant system 120 via the browser 110to perform e-commerce transactions. For example, the user 105 may visitan online store to perform a purchase transaction (e.g., purchasingproducts or services). The user 105 may provide personal data (e.g., anemail address, a mailing address, a phone number, etc.), as well aspayment data (e.g., a personal account number (PAN), a personalidentification number (PIN), a credit card number, a loyalty pointaccount number, a gift card number, bank account number, a socialsecurity number, etc.) in the browser 110 to complete the purchasetransactions. The browser 110 may then provide the personal and paymentdata to the merchant system 120 and/or the processing system 130. Thebrowser 110 may interact with the merchant system 120 to complete thepurchase transactions, and/or may also directly communicate with theprocessing system 130 to complete the purchase transactions.

Still referring to FIG. 1 , the processing system 130 comprises adigital wallet system 140, a transaction system 150, and a tokenizationsystem 160. In one embodiment, the digital wallet system 140 may providedigital wallet service(s) (e.g., offer to enroll in the digit walletservice or to make payments using the digital wallet service) to theuser 105. Further, the digital wallet system 140 may provide a digitalwallet interface to the merchant system 120. The merchant system 120 mayintegrate the digital wallet interface provided by the digital walletsystem 140 to display the digital wallet interface on the browser 110.The user 105 may then utilize the digital wallet interface to performvarious e-commerce transactions (further described below in detail). Thedigital wallet system 140 may communicate with the transaction system150 to perform digital wallet transactions (e.g., digital walletenrollment and services) and purchase transactions.

The transaction system 150 may comprise a plurality of systems,including a server for receiving and storing the sensitive user data.Further, the transaction system 150 may communicate with thetokenization system 160 and the transaction network 170 to perform thedigital wallet transactions and the payment authorization process of thepresent disclosure. The transaction network 170 may include paymentnetworks, issuer systems, and/or acquirer systems facilitate theauthorization or approval of various electronic transaction request(e.g., e-commerce transactions). The transaction system 150 may transmitpayment information (e.g., method of payment, merchant payment tokens,etc.) to the tokenization system 160. The tokenization system 160 maythen tokenize the payment information received from the transactionsystem 150 to generate a token for authenticating and authorizingpurchase transactions. A token may be a low-value token or a high-valuetoken. Further, a token may be a randomly generated number. In otherembodiments, a token may be a pseudorandom number, encryptedinformation, or other character sequence. The processing system 130 maytransmit a token (e.g., a digital wallet token) generated by thetokenization system 160 to the merchant system 120, such that themerchant system 120 may store the token for future transactions. Thetoken may be unique per transaction, per user, and/or per merchant ororganization. Thus, if a given user makes a purchase at merchant A,token A may be generated, but if the user makes a purchase at merchantB, even if the same payment method is used, token B may be generated. Byutilizing a token, the merchant system 120 may not need to send paymentinformation (e.g., debit or credit card information) or other sensitivedata for subsequent transactions, and may instead use the token.Therefore, tokenization may enhance data security as well as merchants'convenience in processing subsequent electronic transactions.

Still referring to FIG. 1 , the processing system 130 may store personaldata and payment data provided by the user 105 in a server(s) or adatabase(s) (not shown) for further processing. Further, the processingsystem 130 may transmit personal data and payment data to the digitalwallet system 140, transaction system 150, and/or tokenization system160 to complete purchase transactions, provide digital walletservice(s), and perform tokenization of payment data (further describedbelow in detail). The processing system 130 may communicate with thetransaction network 170 to authorize payments requested by the merchantsystem 120 based on the personal and payment data provided by the user105 during purchase transactions.

Still referring to FIG. 1 , the processing system 130, may be anintermediary in the system 100 to ensure validity of an electronicpayment request, and to provide digital wallet services and tokenizationservices via the digital wallet system 140 and the tokenization system160, respectively. The processing system 130 may transmit an electronicpayment request (e.g., an authentication request and/or authorizationrequest) to the transaction network 170 and receive a responseindicating a result of the electronic payment request (e.g., anauthentication request and/or an authorization response). For example,when the merchant system 120 transmits an authorization request for anonline purchase transaction, the processing system 130 may act, via thetransaction system 150, as an intermediary for the merchant system 120and transmit the authorization request to the transaction network 170.The processing system 130 may also receive an authorization responsewith a result of the authorization request from the transaction network170, and may transmit the authorization response to the merchant system120.

FIG. 2 shows a block diagram of an exemplary system 200 comprising thebrowser 110, the wallet digital system 140, and the transaction system150. The digital wallet system 140 comprises a software development kit(SDK) server 210, a digital wallet interface 220, an applicationprogramming interface (API) server 230, and a database 240. The SDKserver 210 may provide various SDK functions (or SDK) that the merchantsystem 120 may utilize to interact with the digital wallet interface220. That is, the SDK provided by the SDK server 210 may include classesthat may expose various functions for initiating and processing thedigital wallet services (e.g., an express checkout and a OTPA ortwo-factor authentication (2FA) functionality). In one embodiment, theSDK may be written in European Computer Manufacturer's AssociationScript 6 (ES6) JavaScript. Further, the SDK may be compiled, using awebpack, into a single minified JavaScript (JS) file that may then bedeployed to a cloud storage resource. The cloud storage resource may berestricted to be accessible via a content delivery network serviceendpoint, which may be fronted by an authentication protected domain. Inanother embodiment, alternative deployment method may be utilized by themerchant system 120 in order to securely transmit various paymentinformation stored in the merchant system 120.

Still referring to FIG. 2 , the digital wallet interface 220 is providedto the merchant system 120 to integrate the digital wallet interface 220into the merchant website on the browser 110. The merchant system 120may utilize the SDK provided by the SDK server 210 to integrate thedigital wallet interface 220 and to display on the browser 110. In oneexemplary embodiment, the digital wallet interface 220 may be a Reactapplication using Create React App (CRA). Key libraries of the digitalwallet interface 220, for example, may be predictable state containers(e.g., Redux) for state management (along with React Hooks), a MaterialUser Interface for standard components and cross browser compatibility,Axios for Hypertext Transfer Protocol (HTTP) requests, and SyntacticallyAwesome Style Sheets (SASS) for styling. The digital wallet interface220 may be compiled, for example, using CRA and then deployed to a cloudstorage resource. The cloud storage resource may be restricted to beaccessible via a content delivery network service endpoint, which inturn may be fronted by a basic authentication protected domain. In oneembodiment, the digital wallet interface 220 may be deployed differentlyso that a checkout experience provided by the digital wallet system 140may be securely launched on a per merchant basis.

Still referring to FIG. 2 , the API server 230 may provide various APIsthat the merchant system 120 may utilize to run digital wallet services.For example, the API server 230 may provide a digital wallet API thatmay allow the merchant system 120 to enroll customers in the digitalwallet system 140, authenticate customers, validate an OTPA or 2FA,provide tokens, submit payments, and/or authorize payments via thedigital wallet interface 220 provided on the browser 110. The digitalwallet API may be written in .NET Core backed by a database 240 (e.g.,Structured Query Language (SQL) Server database). The digital wallet APImay be Representational State Transfer (or RESTful) API and may supportJavaScript Object Notation (JSON) format as transaction request andresponse formats. In one embodiment, the digital wallet API may bedocumented with Swagger. The digital wallet API code may be deployed toa web service. The digital wallet API may be restricted to be accessiblevia a content delivery network service endpoint, which in turn may befronted by a basic authentication protected domain.

The methods described hereinafter, by utilizing the systems 100 and 200described above, solve the aforementioned technological problems arisingin the conventional digital wallet technology. That is, the digitalwallet systems and methods of the present disclosure described hereinare directed to an improvement in the conventional digital wallettechnical field and are practically applicable in the field of digitalwallet technology.

FIG. 3 depicts a flowchart of an exemplary method 300 contemplating adigital wallet enrollment at or during guest checkout on the browser 110of the merchant system 120. In the method 300, the user 105 (e.g., acustomer) may shop at a merchant's website and access the merchant'sexisting guest checkout to complete the purchase. During the guestcheckout process, the user 105 may be asked (e.g., via a checkbox) ifthe user 105 would like to opt into a digital wallet or a digital walletservice (e.g., digital wallet express checkout service) of the presentdisclosure. The digital wallet and the digital wallet service may beused interchangeably hereinafter. If the user 105 chooses to opt intothe digital wallet express checkout service, the merchant system 120 maynotify the digital wallet API of the enrollment request of a user (e.g.,the user 105). Upon confirming the purchase by the user 105, the user105 may then be shown an OTPA or 2FA dialog on the digital walletinterface 220 for the user 105 to complete the enrollment with thedigital wallet express checkout service. One exemplary process flow ofthe method 300, performed in accordance with the systems 100 and 200above, is described hereinafter.

In one embodiment, at step 314, the user 105 (e.g., a customer) may additems (e.g., products or services) to a cart displayed on the browser110. The user 105 may then proceed to a guest checkout. At step 316, theuser 105 may fill in the information (e.g., payment, personal, and/orshipping information) necessary to complete a purchase transaction viathe guest checkout. Further, the user 105 may opt into a digital walletservice (e.g., digital wallet express checkout) provided by the digitalwallet system 140. At step 318, the merchant system 120 may process thepurchase order of user 105 by transmitting the order details and paymentrequest data to the processing system 130. The processing system 130 maythen authorize the payment request at step 320 by communicating with thetransaction network 170.

Still referring to FIG. 3 , at step 322, the merchant system 120 mayinitiate an enrollment process for a digital wallet service (e.g.,digital wallet express checkout). At step 324, the digital wallet APIprovided by the API server 230 may save the user information (e.g.,payment information, shipping information, email address, phone number,and/or mailing address) into a server(s) or the database(s) 240, inaccordance with the digital wallet API described in FIG. 2 above. Atstep 326, the digital wallet API may determine whether the paymentinformation sent by the merchant system 120 includes, for example, a PANor a merchant token. At step 328, if the payment information includes aPAN, the tokenization system 160 may tokenize the payment method bygenerating a digital wallet token. At step 330, if the paymentinformation includes a merchant token, the tokenization system 160 mayexchange the merchant token, for example, with the digital wallet tokengenerated by the tokenization system 160. At step 332, the digitalwallet API may then save the merchant token received from the merchantsystem 120 for later processing. In one or more embodiments, thereceived merchant token may be passed along to various processingplatforms.

Still referring to FIG. 3 , at step 334, the digital wallet API mayinitiate an OTPA or 2FA process flow. In one embodiment, an externalOTPA or 2FA service may be used to send, for example, a mobile textmessage (e.g., a short message service (SMS) message) or an email to thephone number and/or the email address provided by the user 105 during adigital wallet service enrollment. In one embodiment, an identificationassociated with the user 105 may be tied to the user's 105 email or aphone number. Further, an OTPA or 2FA six digit code may be sent via amobile text message or an email, which may be used to verify the user105 before the user's 105 data may be used for a payment on one of theacquirer processor's processing platforms.

At step 336, the merchant system 120 may check for the digital walletenrollment status. At step 338, if the digital wallet enrollment statusis no longer pending, the browser 110 may display an order confirmationmessage along with an enrollment error message to the user 105 at step340. If the enrollment status is still pending, however, the browser 110may display the order confirmation page at step 342. At step 344, thedigital wallet interface 220 may then display a prompt to the user 105to request an OTPA or 2FA code (e.g., an OTPA or 2FA six digit code sentvia a mobile text message or an email). At step 346, the digital walletinterface 220 may receive the OTPA or 2FA code entered by the user 105.At step 348, the digital wallet API may validate the OTPA or 2FA code.At step 350, if the OTPA or 2FA is properly validated by the digitalwallet API, the digital wallet API may update the user's 105 digitalwallet enrollment status at step 352. However, if the OTPA or 2FA of theuser 105 cannot be validated, then the digital wallet interface 220 maydisplay a prompt to the user 105 to request for the OTPA or 2FA codeagain. At step 354, the digital wallet interface may display anenrollment confirmation message (e.g., “Thanks for enrolling!”).

FIG. 4 depicts a flowchart of an exemplary method 400 for performing adigital wallet express checkout process with the user 105 (e.g., acustomer) who may have been previously enrolled into the digital walletsystem 140 of the present disclosure. One exemplary process flow of themethod 400, performed in accordance with the systems 100 and 200 above,is described hereinafter.

In one embodiment, at step 402, the user 105 may add items (e.g.,products or services) to a cart provided on the browser 110 of themerchant system 120. In one embodiment, the merchant system 120 mayparticipate in the services provided by the digital wallet of thepresent disclosure. The user 105 may initiate a digital wallet expresscheckout process by selecting a digital wallet express checkout option(e.g., a graphical “express checkout” button) displayed on the browser110. At step 404, the digital wallet interface 220 may display a promptto the user 105 to request the user's 105 personal information (e.g.,name, email address, a phone number, etc.). In one embodiment, thepersonal information, for example an email address, may be auto-filledif the email address is stored in the browser 110 (e.g., in the cookieof the browser 110). At step 406, the digital wallet API may checkwhether the user 105 is enrolled in the digital wallet system 140 of thepresent disclosure. At step 408, if the user 105 is not enrolled in thedigital wallet, the digital wallet interface 220 may then initiate a newuser enrollment process at step 410. If the user 105 is enrolled in thedigital wallet system 140, the digital wallet API may then initiate theOTPA or 2FA flow at step 412, similar to the OTPA or 2FA processdescribed in FIG. 3 above.

Still referring to FIG. 4 , at step 414, the digital wallet interface220 may display a prompt to the user 105 to request for an OTPA or 2FAcode. At step 416, the digital wallet interface 220 may provide the OTPAor 2FA code received from the user 105 to the digital wallet API. Atstep 418, the digital wallet API may validate the received OTPA or 2FAcode. At step 420, if the OTPA or 2FA is not validated, the digitalwallet interface may then display a prompt to the user 105 to request anOTPA or 2FA code again at step 414. If the OTPA or 2FA is validated, thedigital wallet interface 220 may display an OTPA or 2FA confirmationmessage to the user 105 at step 421.

At step 422, the digital wallet API may look up the information (e.g.,shopper identification, name, addresses, payment tokens, etc.)associated with the user 105 enrolled in the digital wallet system 140.At step 424, the digital wallet API may create the user 105 responseobjects (e.g., name, address, payment methods, etc.). In one embodiment,the user 105 information retrieved by the digital wallet API may includevarious methods of payment that may be used to complete the purchasetransaction. For example, the user 105 may use credit card accounts,bank card accounts, and loyalty point accounts. In one embodiment, thedigital wallet interface 220 may present lending options by various cardissuers and lenders at points of checkout to allow the user 105 to payfor products or services in installments. Further, the digital walletAPI may be connected to banks to enable the user 105 to login via bankportals and connect to the user's 105 bank accounts to pay for productsand services online. In one embodiment, the digital wallet interface 220may offer the user 105 one or more options to enroll, sign up for,and/or apply for one or more payment methods during checkout. Forexample, one or more digital wallet APIs may connect the digital walletsystem 140 to the processing system 130 or third party providers tomanage the payment products and/or services of the present disclosure.

At step 426, the digital wallet interface 220 may display the orderreview screen with user response fields prefilled in the order reviewscreen. At step 428, the user 105 may confirm the payment via thedigital wallet interface 220. At step 430, the digital wallet API mayreceive a token from the merchant system 120 along with the paymentconfirmation. At step 432, the tokenization system 160 may exchange themerchant token with the digital wallet token. In one embodiment, thedigital wallet tokens may not be exposed to the merchant system 120. Thedigital wallet tokens may be generated when the user 105 adds paymentmethods and stores the payment methods in the digital wallet “account.”During a payment transaction, the digital wallet token may be exchangedfor the merchant specific token, which may be used for performing apayment authorization. At step 434, the digital wallet API may transmitthe payment request with the merchant specific token to the transactionsystem 150.

Still referring to FIG. 4 , at step 436, the transaction system 150 maycommunicate with the transaction network 170 to perform the paymentauthorization process. At step 438, the digital wallet API may determinewhether the payment authorization is successful. If the paymentauthorization is not successful, the digital wallet interface 220 maydisplay an error message to the user 105 at step 440 and may display theorder review screen again at step 426, so that the user 105 mayre-confirm the payment. In one embodiment, the user 105 may change themethod of payment during re-confirmation. For example, the user 105 mayswitch from using a credit card account to a debit card account toconfirm the payment. If the payment authorization is successful, thedigital wallet interface 220 may display a success message to the user105 and redirect the user 105 back to the merchant's browser 110 at step442. The browser 110 may then display any suitable message (e.g., “Thankyou for shopping!”) determined by the merchant system 120 for confirmingthe payment transaction at step 446.

FIG. 5 depicts a flowchart of an exemplary method 500 for performing adigital wallet express checkout process with the user 105 (e.g., acustomer) who may not be enrolled in the digital wallet system 140 ofthe present disclosure. In the method 500, the digital wallet interface220 may walk the user 105 through enrollment and completion of a digitalwallet transaction. Thereafter, the user 105 may be redirected back tothe order confirmation page of the merchant's browser 110. One exemplaryprocess flow of the method 500, performed in accordance with the systems100 and 200 above, is described hereinafter.

In one embodiment, at step 502, the user 105 may add items to a cartdisplayed on the browser 110 and may initiate a digital wallet expresscheckout process of the present disclosure. At step 504, the digitalwallet interface 220 may display a prompt to the user 105 to request theemail address of user 105. At step 506, the digital wallet API may checkwhether the user 105 is enrolled in the digital wallet system 140 of thepresent disclosure. At step 508, if the digital wallet API determinesthat the user 105 is enrolled in a digital wallet service (e.g., thedigital wallet express checkout), an existing user payment process maybe performed. For example, the digital wallet express checkout processfor the previously enrolled user as described in FIG. 4 above may beperformed at step 510. If the digital wallet API determines that theuser 105 is not enrolled in the digital wallet express checkout at step508, the digital wallet interface 220 may display a prompt to request aphone number from the user 105 at step 512.

Still referring to FIG. 5 , at step 514, the digital wallet interface220 may initiate a digital wallet enrolment process. At step 516, thedigital wallet API may save the user's 105 information into the database240 at step 516. At step 518, the digital wallet API may initiate anOTPA or 2FA flow. At step 520, the digital wallet interface 220 maydisplay a prompt to request an OTPA or 2FA code from the user 105. Atstep 522, the user 105 may provide the OTPA or 2FA code to the digitalwallet interface 220. At step 524, the digital wallet API may validatethe OTPA or 2FA code received from the user 105. If the digital walletAPI validates the OTPA or 2FA at step 526, the digital wallet API mayupdate the user 105 enrollment status as being verified at step 528. Ifthe digital wallet API cannot validate the OTPA or 2FA, the digitalwallet interface 220 may then display a prompt to the user 105 torequest the OTPA or 2FA code again at step 520. At step 530, the digitalwallet interface 220 may display an enrollment confirmation message atstep 530. At step 532, the digital wallet interface 220 may display aprompt to the user 105 to request a shipping address from the user 105.

Still referring to FIG. 5 , at step 534, the digital wallet API may savethe shipping address received from the user 105. At step 536, thedigital wallet interface 220 may display a prompt to request a paymentmethod from the user 105. At step 538, the digital wallet API mayrequest a tokenization of the payment method selected by the user 105.At step 540, the tokenization system 160 may generate a digital wallettoken for the payment method selected by the user 105. At step 542, thedigital wallet API may store the digital wallet token generated by thetokenization system 160 in the database 240. At step 554, the digitalwallet API may determine whether the payment method has beensuccessfully saved. If the payment has not been saved successfully bythe digital wallet API, the digital wallet interface 220 may display aprompt to the user 105 again to request a payment method. If the paymenthas been saved successfully by the digital wallet API, the digitalwallet interface 220 may display an order review screen at 546. At step548, the user 105 may confirm the payment of the purchase on the digitalwallet interface 220. At step 550, the digital wallet API may receive atoken from the merchant system 120. At step 552, the tokenization system160 may exchange the generated digital wallet token with the tokenreceived from the merchant system 120.

Still referring to FIG. 5 , at step 554, the digital wallet API may senda payment request to the transaction system 150 to request processing ofthe payment. At step 556, the transaction system 150 may communicatewith the transaction network 170 to authorize the payment. At step 558,the digital wallet API may determine whether the payment is successful.If the payment is not authorized, the digital wallet interface 220 maythen display an error message to the user 105 at step 560. The digitalwallet interface 220 may then display a prompt to the user 105 torequest for the payment method again at step 536. If the payment issuccessfully authorized, the digital wallet interface 220 may display asuccess message and redirect the user 105 back to the merchant websiteon the browser 110 at step 562. At step 564, the browser 110 may thendisplay a suitable message (e.g., “Thank you for shopping!”) determinedby the merchant system 120.

FIG. 6 depicts a flowchart of an exemplary method 600 for performing adigital wallet express checkout process with the user 105 (e.g., acustomer) who may use a guest checkout link or option to start thecheckout process on a merchant's website. In the method 600, themerchant system 120 may be integrated with the digital wallet of thepresent disclosure. As such, when the user 105 enters the email address,the user 105 may be prompted to use the digital wallet express checkoutinstead of proceeding with the guest checkout. One exemplary processflow of the method 600, performed in accordance with the systems 100 and200 above, is described hereinafter.

In one embodiment, at step 602, the user 105 may add items to a cartdisplayed on the browser 110 and may proceed to a guest checkoutprovided by the browser 110. At step 604, the user 105 may enter anemail address into the browser 110. At step 606, the digital walletinterface 220 may proceed to initiate the process of checking if theuser 105 is enrolled in the digital wallet system 140 of the presentdisclosure (e.g., receive input (e.g., an email address or a phonenumber) from the user). At step 608, the digital wallet API may check ifthe user 105 is enrolled in the digital wallet express checkout. If thedigital wallet interface 220 determines that the user 105 is notenrolled in the digital wallet express checkout at step 610, then theguest checkout process in accordance with the merchant system 120 may beperformed at step 612. If the user 105 is enrolled in the digital walletexpress checkout, the digital wallet interface 220 may display a promptto the user 105 at step 614 to determine whether the user 105 wishes tocontinue the digital wallet express checkout process at step 616. If theuser 105 does not wish to continue with the digital wallet expresscheckout, then the guest checkout process in accordance with themerchant system 120 may be performed at step 612. At step 618, if theuser 105 wishes to continue with the digital wallet express checkoutflow, the digital wallet API may initiate the OTPA or 2FA process. Atstep 620, the digital wallet system 140 may continue with the digitalexpress checkout process as described in FIGS. 4 and 5 above.

FIGS. 7A-8B show exemplary graphical user interfaces of the browser 110and the digital wallet interface 220. FIGS. 7A-8B may be describedhereinafter in tandem with the flowcharts depicted in FIGS. 9A-B forperforming exemplary methods of performing electronic transactions usingthe digital wallet system 140 of the present disclosure.

FIG. 9A depicts a flowchart of an exemplary method for performing anelectronic transaction using the digital wallet system 140 of thepresent disclosure. In one embodiment, a method 900 may be performed bythe processing system 130 (e.g., the digital wallet system 140,transaction system 150, and the tokenization system 160 thereof). In oneembodiment, at step 902, the digital wallet system 140 may receive adigital wallet express checkout request from the user 105 in order toprocess an order on a merchant's website on the browser 110. Forexample, the user 105 may interact with the merchant's webpage 700 asshown in FIG. 7A. In one embodiment, the webpage 700 may include ashopping item section 702, promotion section 704, and a checkout section706. The checkout section 706 may display purchase order information(e.g., order total), express checkout button 708 (e.g., digital walletexpress checkout), and/or a guest checkout button 710. In oneembodiment, the user 105 may request the digital wallet express checkoutby pressing the express checkout button 708.

When the user 105 presses the express checkout button 708, the digitalwallet interface 220 may display a prompt to the user 105 for enteringan email address at step 904. For example, the digital wallet interface220 may provide an express checkout window 802 of a graphical userinterface 800 as shown in FIG. 8A. The express checkout window 802 mayinclude an email address input field 806 and a button 808 for continuingthe express checkout. The user 105 may enter an email address in theemail address input field 806. At step 906, the digital wallet system140 may determine whether the user 105 is enrolled in the digital walletsystem 140 based on the email address received in the email addressinput field 806. If the user 105 is enrolled in the digital walletsystem 140, the digital wallet system 140 may display a prompt to theuser 105 to determine whether the user 105 wishes to continue with theexpress checkout. In one embodiment, the user 105 may continue theexpress checkout by pressing an express checkout continue button 808. Atstep 908, the digital wallet system 140 may perform an OTPA or 2FA withthe user 105. In one embodiment, the digital wallet API may send an OTPAor 2FA code to the user 105 via the user's 105 email address or phonenumber stored in the digital wallet system 140. The digital walletinterface 220 may then display an OTPA or 2FA prompt 812 on a paymenttransaction information interface 810 as shown in FIG. 8B. The user 105may then enter an OTPA or 2FA code (e.g., a six-digit OTPA or 2FA code)into the OTPA or 2FA prompt 812.

Still referring to FIG. 9A, upon validating the OTPA or 2FA at step 908,the digital wallet interface 220 may display an order review andselection options and/or an input field(s) for indicating the method ofpayment to the user 105 at step 910. At step 912, the digital walletsystem 140 may then receive the method of payment and order confirmationfrom the user 105. At step 914, the tokenization system 160 may tokenizethe payment method provided by the user 105 and/or exchange a digitalwallet token with a merchant specific token received from the merchantsystem 120, in the similar manner as described in FIGS. 1-5 above.Further, the transaction system 150 may communicate with the transactionnetwork 170 to authorize and complete the payment, in the similar manneras described in FIGS. 1-6 above. At step 916, the browser 110 maydisplay a message indicating the result of the payment to the user 105.

Still referring to FIG. 9A, if the user 105 is not enrolled in thedigital wallet system 140 at step 906, the digital wallet system 140 mayinitiate an enrollment process at step 918. The digital wallet system140 may then process the enrollment by performing an OTPA or 2FA withthe user 105 at step 920 in the similar manner as disclosed above atstep 908. At step 922, upon verification of the OTPA or 2FA performed atstep 920, the digital wallet system 140 may create a digital walletaccount for the user 105 and save the user 105 information into thedigital wallet system 140 (e.g., in the database 240). Further, thedigital wallet interface 220 may display an enrollment confirmationmessage to the user 105 after the user 105 has been enrolled into thedigital wallet system 140. After enrolling the user 105 into the digitalwallet system 140, the digital wallet system 140 may proceed to step 910to complete the payment transaction as described above.

FIG. 9B depicts a flowchart of another exemplary method for performingan electronic transaction using the digital wallet system 140 of thepresent disclosure. In one embodiment, a method 930 may be performed bythe processing system 130 (e.g., the digital wallet system 140,transaction system 150, and the tokenization system 160 thereof). Atstep 932, the digital wallet system 140 may receive a guest checkoutrequest from the user 105 in order to process an order on a merchant'swebsite on the browser 110. For example, the user 105 may select theguest checkout button 710 as shown in the webpage 700 of FIG. 7A.

Still referring to FIG. 9B, the browser 110 may display a prompt to theuser 105 for selecting an option to opt into a digital wallet expresscheckout at step 934. In one embodiment, the browser 110 may show aguest checkout window 720 as shown in FIG. 7B. The guest checkout window720 may include a payment information section 722, a digital walletexpress checkout opt-in section 724, and/or a payment confirmationbutton 726. If the user 105 selects the check box shown in the opt-insection 724, the transaction system 150 may process the order made bythe user 105 and may authorize the payment by communicating with thetransaction network 170 at step 938. After completing the payment atstep 938, the digital wallet system 140 may perform an OTPA or 2FA withthe user 105 at step 940 in the similar manner described above in FIG.9A at steps 908 and 920. Upon verifying the OTPA or 2FA authenticationwith the user 105, the digital wallet system 140 may enroll the user 105into the digital wallet system 140. The merchant website 700 of thebrowser 110, may then display an enrollment confirmation message to theuser at step 942.

Still referring to FIG. 9B, if the user 105 does not opt into thedigital wallet express checkout option at step 934, the digital walletinterface 220 may display a prompt to the user requesting to enter anemail address or a phone number at step 944. At step 946, the digitalwallet system 140 may then automatically determine whether the user 105is enrolled in the digital wallet system 140 based on the email addressor the phone number provided by the user 105 at step 944. If the user105 is not enrolled in the digital wallet system 140, the processingsystem 130 may then proceed to step 950 to process the order andauthorize the payment in the similar manner as described at step 936.However, if the user 105 is determined to be enrolled in the digitalwallet system 140, based on the email address and the phone numberprovided by the user 105, then the digital wallet interface 220 mayperform the express checkout process at step 948 in the similar manneras described at steps 908-916 in FIG. 9A.

FIG. 9C depicts a flowchart of yet another exemplary method 960 forperforming an electronic transaction using the digital wallet system140, according to one aspect of the present disclosure. In oneembodiment, a method 960 may be performed by the processing system 130(e.g., the digital wallet system 140, transaction system 150, and thetokenization system 160 thereof).

At step 962, the processing system 130 may receive, from the browser 110(e.g., an electronic transaction browser), a guest checkout request andelectronic transaction information. The electronic transactioninformation may include user data, and the guest checkout request mayinclude a digital wallet enrollment request. In one embodiment, theelectronic transaction information comprises at least one of an emailaddress or a phone number. At step 964, the digital wallet system 140may determine whether a user (e.g., user 105) is enrolled in the digitalwallet system 140. At step 966, the digital wallet system 140 mayauthorize an electronic transaction based on the electronic transactioninformation upon determining the user 105 is not enrolled in the digitalwallet system 140. At step 968, the digital wallet system 140 mayinitiate a digital wallet enrollment upon authorizing the electronictransaction. At step 970, the digital wallet system 140 may store theuser data in the digital wallet system 140. At step 972, the digitalwallet system 140 may transmit a user verification request to thebrowser 110. In one embodiment, the user verification request mayinclude an OTP or a two-factor authentication request. At step 974, thedigital wallet system 140 may receive a user verification response fromthe browser 110. At step 976, the digital wallet system 140 may generatea digital wallet enrollment status message based on the userverification response. In one embodiment, the digital wallet system 140may generate a token based on the electronic transaction information.Further, the digital wallet system 140 may generate and display aplurality of transaction options for completing the electronictransaction. In one embodiment, the plurality of options for completingthe electronic transaction may comprise at least one of payment with acredit card account, payment with loyalty points, payment by lending, orpayment with a bank account.

In addition to a standard desktop, or server, it is fully within thescope of this disclosure that any computer system capable of therequired storage and processing demands would be suitable for practicingthe embodiments of the present disclosure. This may include tabletdevices, smart phones, pin pad devices, and any other computer devices,whether mobile or even distributed on a network (i.e., cloud based).

Unless specifically stated otherwise, as apparent from the followingdiscussions, it is appreciated that throughout the specificationdiscussions utilizing terms such as “processing,” “computing,”“calculating,” “determining”, analyzing” or the like, refer to theaction and/or processes of a computer or computing system, or similarelectronic computing device, that manipulate and/or transform datarepresented as physical, such as electronic, quantities into other datasimilarly represented as physical quantities.

In a similar manner, the term “processor” may refer to any device orportion of a device that processes electronic data, e.g., from registersand/or memory to transform that electronic data into other electronicdata that, e.g., may be stored in registers and/or memory. A “computer,”a “computing machine,” a “computing platform,” a “computing device,” ora “server” may include one or more processors.

FIG. 10 illustrates a computer system designated 1000. The computersystem 1000 can include a set of instructions that can be executed tocause the computer system 1000 to perform any one or more of the methodsor computer based functions disclosed herein. The computer system 1000may operate as a standalone device or may be connected, e.g., using anetwork, to other computer systems or peripheral devices.

In a networked deployment, the computer system 1000 may operate in thecapacity of a server or as a client user computer in a server-clientuser network environment, or as a peer computer system in a peer-to-peer(or distributed) network environment. The computer system 1000 can alsobe implemented as or incorporated into various devices, such as apersonal computer (PC), a tablet PC, a set-top box (STB), a personaldigital assistant (PDA), a mobile device, a palmtop computer, a laptopcomputer, a desktop computer, a communications device, a wirelesstelephone, a land-line telephone, a control system, a camera, a scanner,a facsimile machine, a printer, a pager, a personal trusted device, aweb appliance, a network router, switch or bridge, or any other machinecapable of executing a set of instructions (sequential or otherwise)that specify actions to be taken by that machine. In a particularimplementation, the computer system 1000 can be implemented usingelectronic devices that provide voice, video, or data communication.Further, while a single computer system 1000 is illustrated, the term“system” shall also be taken to include any collection of systems orsub-systems that individually or jointly execute a set, or multiplesets, of instructions to perform one or more computer functions.

As illustrated in FIG. 10 , the computer system 1000 may include aprocessor 1002, e.g., a central processing unit (CPU), a graphicsprocessing unit (GPU), or both. The processor 1002 may be a component ina variety of systems. For example, the processor 1002 may be part of astandard personal computer or a workstation. The processor 1002 may beone or more general processors, digital signal processors, applicationspecific integrated circuits, field programmable gate arrays, servers,networks, digital circuits, analog circuits, combinations thereof, orother now known or later developed devices for analyzing and processingdata. The processor 1002 may implement a software program, such as codegenerated manually (i.e., programmed).

The computer system 1000 may include a memory 1004 that can communicatevia a bus 1008. The memory 1004 may be a main memory, a static memory,or a dynamic memory. The memory 1004 may include, but is not limited tocomputer readable storage media such as various types of volatile andnon-volatile storage media, including but not limited to random accessmemory, read-only memory, programmable read-only memory, electricallyprogrammable read-only memory, electrically erasable read-only memory,flash memory, magnetic tape or disk, optical media and the like. In oneimplementation, the memory 1004 includes a cache or random-access memoryfor the processor 1002. In alternative implementations, the memory 1004is separate from the processor 1002, such as a cache memory of aprocessor, the system memory, or other memory. The memory 1004 may be anexternal storage device or database for storing data. Examples include ahard drive, compact disc (“CD”), digital video disc (“DVD”), memorycard, memory stick, floppy disc, universal serial bus (“USB”) memorydevice, or any other device operative to store data. The memory 1004 isoperable to store instructions executable by the processor 1002. Thefunctions, acts or tasks illustrated in the figures or described hereinmay be performed by the programmed processor 1002 executing theinstructions stored in the memory 1004. The functions, acts or tasks areindependent of the particular type of instructions set, storage media,processor or processing strategy and may be performed by software,hardware, integrated circuits, firm-ware, micro-code and the like,operating alone or in combination. Likewise, processing strategies mayinclude multiprocessing, multitasking, parallel processing and the like.

As shown, the computer system 1000 may further include a display unit1010, such as a liquid crystal display (LCD), an organic light emittingdiode (OLED), a flat panel display, a solid-state display, a cathode raytube (CRT), a projector, a printer or other now known or later developeddisplay device for outputting determined information. The display 1010may act as an interface for the user to see the functioning of theprocessor 1002, or specifically as an interface with the software storedin the memory 1004 or in the drive unit 1006.

Additionally or alternatively, the computer system 1000 may include aninput device 1012 configured to allow a user to interact with any of thecomponents of system 1000. The input device 1012 may be a number pad, akeyboard, or a cursor control device, such as a mouse, or a joystick,touch screen display, remote control, or any other device operative tointeract with the computer system 1000.

The computer system 1000 may also or alternatively include a disk oroptical drive unit 1006. The disk drive unit 1006 may include acomputer-readable medium 1022 in which one or more sets of instructions1024, e.g., software, can be embedded. Further, the instructions 1024may embody one or more of the methods or logic as described herein. Theinstructions 1024 may reside completely or partially within the memory1004 and/or within the processor 1002 during execution by the computersystem 1000. The memory 1004 and the processor 1002 also may includecomputer-readable media as discussed above.

In some systems, a computer-readable medium 1022 includes instructions1024 or receives and executes instructions 1024 responsive to apropagated signal so that a device connected to a network 1030 cancommunicate voice, video, audio, images, or any other data over thenetwork 1030. Further, the instructions 1024 may be transmitted orreceived over the network 1030 via a communication port or interface1020, and/or using a bus 1008. The communication port or interface 1020may be a part of the processor 1002 or may be a separate component. Thecommunication port 1020 may be created in software or may be a physicalconnection in hardware. The communication port 1020 may be configured toconnect with a network 1030, external media, the display 1010, or anyother components in system 1000, or combinations thereof. The connectionwith the network 1030 may be a physical connection, such as a wiredEthernet connection or may be established wirelessly as discussed below.Likewise, the additional connections with other components of the system1000 may be physical connections or may be established wirelessly. Thenetwork 1030 may alternatively be directly connected to the bus 1008.

While the computer-readable medium 1022 is shown to be a single medium,the term “computer-readable medium” may include a single medium ormultiple media, such as a centralized or distributed database, and/orassociated caches and servers that store one or more sets ofinstructions. The term “computer-readable medium” may also include anymedium that is capable of storing, encoding, or carrying a set ofinstructions for execution by a processor or that cause a computersystem to perform any one or more of the methods or operations disclosedherein. The computer-readable medium 1022 may be non-transitory, and maybe tangible.

The computer-readable medium 1022 can include a solid-state memory suchas a memory card or other package that houses one or more non-volatileread-only memories. The computer-readable medium 1022 can be arandom-access memory or other volatile re-writable memory. Additionallyor alternatively, the computer-readable medium 1022 can include amagneto-optical or optical medium, such as a disk or tapes or otherstorage device to capture carrier wave signals such as a signalcommunicated over a transmission medium. A digital file attachment to ane-mail or other self-contained information archive or set of archivesmay be considered a distribution medium that is a tangible storagemedium. Accordingly, the disclosure is considered to include any one ormore of a computer-readable medium or a distribution medium and otherequivalents and successor media, in which data or instructions may bestored.

In an alternative implementation, dedicated hardware implementations,such as application specific integrated circuits, programmable logicarrays and other hardware devices, can be constructed to implement oneor more of the methods described herein. Applications that may includethe apparatus and systems of various implementations can broadly includea variety of electronic and computer systems. One or moreimplementations described herein may implement functions using two ormore specific interconnected hardware modules or devices with relatedcontrol and data signals that can be communicated between and throughthe modules, or as portions of an application-specific integratedcircuit. Accordingly, the present system encompasses software, firmware,and hardware implementations.

The computer system 1000 may be connected to one or more networks 1030.The network 1030 may define one or more networks including wired orwireless networks. The wireless network may be a cellular telephonenetwork, an 802.11, 802.16, 802.20, or WiMAX network. Further, suchnetworks may include a public network, such as the Internet, a privatenetwork, such as an intranet, or combinations thereof, and may utilize avariety of networking protocols now available or later developedincluding, but not limited to TCP/IP based networking protocols. Thenetwork 1030 may include wide area networks (WAN), such as the Internet,local area networks (LAN), campus area networks, metropolitan areanetworks, a direct connection such as through a Universal Serial Bus(USB) port, or any other networks that may allow for data communication.The network 1030 may be configured to couple one computing device toanother computing device to enable communication of data between thedevices. The network 1030 may generally be enabled to employ any form ofmachine-readable media for communicating information from one device toanother. The network 1030 may include communication methods by whichinformation may travel between computing devices. The network 1030 maybe divided into sub-networks. The sub-networks may allow access to allof the other components connected thereto or the sub-networks mayrestrict access between the components. The network 1030 may be regardedas a public or private network connection and may include, for example,a virtual private network or an encryption or other security mechanismemployed over the public Internet, or the like.

In accordance with various implementations of the present disclosure,the methods described herein may be implemented by software programsexecutable by a computer system. Further, in an exemplary, non-limitedimplementation, implementations can include distributed processing,component/object distributed processing, and parallel processing.Alternatively, virtual computer system processing can be constructed toimplement one or more of the methods or functionality as describedherein.

Although the present specification describes components and functionsthat may be implemented in particular implementations with reference toparticular standards and protocols, the disclosure is not limited tosuch standards and protocols. For example, standards for Internet andother packet switched network transmission (e.g., TCP/IP, UDP/IP, HTML,HTTP, etc.) represent examples of the state of the art. Such standardsare periodically superseded by faster or more efficient equivalentshaving essentially the same functions. Accordingly, replacementstandards and protocols having the same or similar functions as thosedisclosed herein are considered equivalents thereof.

It will be understood that the steps of methods discussed are performedin one embodiment by an appropriate processor (or processors) of aprocessing (i.e., computer) system executing instructions(computer-readable code) stored in storage. It will also be understoodthat the disclosed embodiments are not limited to any particularimplementation or programming technique and that the disclosedembodiments may be implemented using any appropriate techniques forimplementing the functionality described herein. The disclosedembodiments are not limited to any particular programming language oroperating system.

It should be appreciated that in the above description of exemplaryembodiments, various features of the embodiments are sometimes groupedtogether in a single embodiment, figure, or description thereof for thepurpose of streamlining the disclosure and aiding in the understandingof one or more of the various inventive aspects. This method ofdisclosure, however, is not to be interpreted as reflecting an intentionthat a claimed embodiment requires more features than are expresslyrecited in each claim. Rather, as the following claims reflect,inventive aspects lie in less than all features of a single foregoingdisclosed embodiment. Thus, the claims following the DetailedDescription are hereby expressly incorporated into this DetailedDescription, with each claim standing on its own as a separateembodiment.

Furthermore, while some embodiments described herein include some butnot other features included in other embodiments, combinations offeatures of different embodiments are meant to be within the scope ofthe present disclosure, and form different embodiments, as would beunderstood by those skilled in the art. For example, in the followingclaims, any of the claimed embodiments can be used in any combination.

Furthermore, some of the embodiments are described herein as a method orcombination of elements of a method that can be implemented by aprocessor of a computer system or by other means of carrying out thefunction. Thus, a processor with the necessary instructions for carryingout such a method or element of a method forms a means for carrying outthe method or element of a method. Furthermore, an element describedherein of an apparatus embodiment is an example of a means for carryingout the function performed by the element for the purpose of carryingout the function.

In the description provided herein, numerous specific details are setforth. However, it is understood that embodiments of the presentdisclosure may be practiced without these specific details. In otherinstances, well-known methods, structures and techniques have not beenshown in detail in order not to obscure an understanding of thisdescription.

Similarly, it is to be noticed that the term coupled, when used in theclaims, should not be interpreted as being limited to direct connectionsonly. The terms “coupled” and “connected,” along with their derivatives,may be used. It should be understood that these terms are not intendedas synonyms for each other. Thus, the scope of the expression a device Acoupled to a device B should not be limited to devices or systemswherein an output of device A is directly connected to an input ofdevice B. It means that there exists a path between an output of A andan input of B which may be a path including other devices or means.“Coupled” may mean that two or more elements are either in directphysical or electrical contact, or that two or more elements are not indirect contact with each other but yet still co-operate or interact witheach other.

Thus, while there has been described what are believed to be thepreferred embodiments of the present disclosure, those skilled in theart will recognize that other and further modifications may be madethereto without departing from the spirit of the present disclosure, andit is intended to claim all such changes and modifications as fallingwithin the scope of the present disclosure. For example, any formulasgiven above are merely representative of procedures that may be used.Functionality may be added or deleted from the block diagrams andoperations may be interchanged among functional blocks. Steps may beadded or deleted to methods described within the scope of the presentdisclosure.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other implementations, which fallwithin the true spirit and scope of the present disclosure. Thus, to themaximum extent allowed by law, the scope of the present disclosure is tobe determined by the broadest permissible interpretation of thefollowing claims and their equivalents, and shall not be restricted orlimited by the foregoing detailed description. While variousimplementations of the disclosure have been described, it will beapparent to those of ordinary skill in the art that many moreimplementations and implementations are possible within the scope of thedisclosure. Accordingly, the disclosure is not to be restricted exceptin light of the attached claims and their equivalents.

What is claimed is:
 1. A system for a tokenized digital wallet service for a secure online transaction, comprising: one or more processors; a data storage storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising: receiving, by a merchant system, an authorization request for an online transaction from a user interface of a device associated with a user displaying a website hosted by the merchant system, wherein the authorization request includes user information, transaction information, or a combination thereof; transmitting, by the merchant system, the authorization request to a digital wallet system; determining the authorization request for the online transaction authorization is unsuccessful; generating an error notification in the user interface of the device associated with the user, wherein the error notification includes a review screen for the user to re-confirm the transaction information, and wherein the re-confirmation includes the user switching a payment method; processing, by the digital wallet system, the authorization request to initiate the online transaction, wherein the digital wallet system generates a digital wallet interface that is integrated by the merchant system for display on the user interface of the device; determining, upon initiating the online transaction, that the user is not registered with the digital wallet service; registering, by the digital wallet system via the user interface of the device, the user with the digital wallet service; generating, by the digital wallet system, a first token based, at least in part, on the user information, the transaction information, or a combination thereof; and exchanging, by the digital wallet system, the first token with a second token associated with a service provider to authorize the online transaction, wherein the service provider is registered with the digital wallet service.
 2. The system of claim 1, wherein registering the user for the digital wallet service, further comprises: generating, by the digital wallet system, a presentation of a digital wallet interface element within the user interface of the device associated with the user, wherein the digital wallet interface includes a one-time password authentication request or a two-factor authentication request; and receiving, via the user interface of the device, a one-time password or an activation of the two-factor authentication to register for the digital wallet service.
 3. The system of claim 2, further comprising: checking, by the digital wallet system, registration status of the user with the digital wallet service; determining, by the digital wallet system, pendency of the registration for the digital wallet service has exceeded a time threshold; generating, by the digital wallet system, a notification in the user interface of the device requesting for the one-time password or a two-factor authentication code; and validating, by the digital wallet system, the one-time password or the two-factor authentication code to approve the registration for the digital wallet service.
 4. The system of claim 1, further comprising: determining the user information, the transaction information, the first token, the second token, or a combination thereof is not saved in a database; generating a presentation in the user interface of the device requesting the user information, the transaction information, the first token, the second token, or a combination thereof; and storing the user information, the transaction information, the first token, the second token, or a combination thereof in the database.
 5. The system of claim 1, wherein the digital wallet system includes a software development kit that is compiled in a Javascript to perform an express checkout, a one-time password authentication, or a two-factor authentication.
 6. The system of claim 1, wherein the token is a low-value token, a high-value token, a randomly generated number, a pseudorandom number, a character sequence, or a combination thereof.
 7. The system of claim 6, wherein the token is encrypted, and wherein the encrypted token is unique for each of the online transaction, the user, the service provider, or a combination thereof.
 8. The system of claim 1, further comprising: providing an express checkout service, a tokenization service, an auto-populating service that fills data fields in electronic transaction browsers with saved user information, or a combination thereof for the user registered with the digital wallet service.
 9. The system of claim 1, wherein the transaction information includes a personal account number (PAN), a personal identification number (PIN), a credit card number, a bank account number, a social security number, or a combination thereof.
 10. A computer-implemented method for a tokenized digital wallet service for a secure online transaction, comprising: receiving, by a merchant system, an authorization request for an online transaction from a user interface of a device associated with a user displaying a website hosted by the merchant system, wherein the authorization request includes user information, transaction information, or a combination thereof; transmitting, by the merchant system, the authorization request to a digital wallet system; determining the authorization request for the online transaction authorization is unsuccessful; generating an error notification in the user interface of the device associated with the user, wherein the error notification includes a review screen for the user to re-confirm the transaction information, and wherein the re-confirmation includes the user switching a payment method; processing, by the digital wallet system, the authorization request to initiate the online transaction, wherein the digital wallet system generates a digital wallet interface that is integrated by the merchant system for display on the user interface of the device; determining, upon initiating the online transaction, that the user is not registered with the digital wallet service; registering, by the digital wallet system via the user interface of the device, the user with the digital wallet service; generating, by the digital wallet system, a first token based, at least in part, on the user information, the transaction information, or a combination thereof; and exchanging, by the digital wallet system, the first token with a second token associated with a service provider to authorize the online transaction, wherein the service provider is registered with the digital wallet service.
 11. The computer-implemented method of claim 10, wherein registering the user for the digital wallet service, further comprises: generating, by the digital wallet system, a presentation of a digital wallet interface element within the user interface of the device associated with the user, wherein the digital wallet interface includes a one-time password authentication request or a two-factor authentication request; and receiving, via the user interface of the device, a one-time password or an activation of the two-factor authentication to register for the digital wallet service.
 12. The computer-implemented method of claim 11, further comprising: checking, by the digital wallet system, registration status of the user with the digital wallet service; determining, by the digital wallet system, pendency of the registration for the digital wallet service has exceeded a time threshold; generating, by the digital wallet system, a notification in the user interface of the device requesting for the one-time password or a two-factor authentication code; and validating, by the digital wallet system, the one-time password or the two-factor authentication code to approve the registration for the digital wallet service.
 13. The computer-implemented method of claim 10, further comprising: determining the user information, the transaction information, the first token, the second token, or a combination thereof is not saved in a database; generating a presentation in the user interface of the device requesting the user information, the transaction information, the first token, the second token, or a combination thereof; and storing the user information, the transaction information, the first token, the second token, or a combination thereof in the database.
 14. The computer-implemented method of claim 10, wherein the digital wallet system includes a software development kit that is compiled in a Javascript to perform an express checkout, a one-time password authentication, or a two-factor authentication.
 15. The computer-implemented method of claim 10, wherein the token is a low-value token, a high-value token, a randomly generated number, a pseudorandom number, a character sequence, or a combination thereof.
 16. A non-transitory computer readable medium for a tokenized digital wallet service for a secure online transaction, the non-transitory computer readable medium storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations, comprising: receiving, by a merchant system, an authorization request for an online transaction from a user interface of a device associated with a user displaying a website hosted by the merchant system, wherein the authorization request includes user information, transaction information, or a combination thereof; transmitting, by the merchant system, the authorization request to a digital wallet system; determining the authorization request for the online transaction authorization is unsuccessful; generating an error notification in the user interface of the device associated with the user, wherein the error notification includes a review screen for the user to re-confirm the transaction information, and wherein the re-confirmation includes the user switching a payment method; processing, by the digital wallet system, the authorization request to initiate the online transaction, wherein the digital wallet system generates a digital wallet interface that is integrated by the merchant system for display on the user interface of the device; determining, upon initiating the online transaction, that the user is not registered with the digital wallet service; registering, by the digital wallet system via the user interface of the device, the user with the digital wallet service; generating, by the digital wallet system, a first token based, at least in part, on the user information, the transaction information, or a combination thereof; and exchanging, by the digital wallet system, the first token with a second token associated with a service provider to authorize the online transaction, wherein the service provider is registered with the digital wallet service.
 17. The non-transitory computer readable medium of claim 16, wherein registering the user for the digital wallet service, further comprises: generating, by the digital wallet system, a presentation of a digital wallet interface element within the user interface of the device associated with the user, wherein the digital wallet interface includes a one-time password authentication request or a two-factor authentication request; and receiving, via the user interface of the device, a one-time password or an activation of the two-factor authentication to register for the digital wallet service.
 18. The non-transitory computer readable medium of claim 17, further comprising: checking, by the digital wallet system, registration status of the user with the digital wallet service; determining, by the digital wallet system, pendency of the registration for the digital wallet service has exceeded a time threshold; generating, by the digital wallet system, a notification in the user interface of the device requesting for the one-time password or a two-factor authentication code; and validating, by the digital wallet system, the one-time password or the two-factor authentication code to approve the registration for the digital wallet service. 